home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Sun Solutions 2000 #2
/
Sun Solutions CD (Volume 2 2000)(Special Focus - Java Technologies)(Disc 1).ISO
/
products
/
Software
/
BostonBusinessComputing
/
bbc
/
README.Vbackup
< prev
next >
Wrap
Text File
|
2000-02-11
|
5KB
|
143 lines
README
======
Vbackup version 3.23
Copyright 1989-2000 Boston Business Computing
1. Introduction
===============
Thank you for selecting Vbackup from Boston Business Computing.
This file contains the following sections:
1. Introduction
2. Installation
3. Technical Support
4. System-Specific Release Notes
4.1 IBM AIX
4.2 SGI IRIX
4.3 Solaris
4.4 SCO
4.5 Other systems
5. Known Problems and Limitations
The documentation for Vbackup consists of the "Vbackup Reference Guide",
the "Installation and Troubleshooting" booklet, the online UNIX man page,
and, for VCL users, the online VCL help library.
The ID.Vbackup file describes all files in the Vbackup release.
2. Installation
===============
Please refer to the "Installation and Troubleshooting" booklet.
3. Technical Support
====================
Purchasing Vbackup entitles you to sixty days of free phone support via
our Technical Support Line. The support line can be reached at (978)
725-3222. Hours are 9:00-5:00 (Eastern) Monday through Friday. Please
have your product serial number or maintenance authorization number
available when you call. If you prefer, you may communicate problems,
questions, or enhancement requests via FAX (send to Vbackup Support at
(978) 725-3229) or email (sales@bosbc.com). We make every effort to
respond to queries from supported customers within two business days.
Extended support can be purchased for an additional charge. Extended
support entitles you to access to the Technical Support Line, priority
bug fixes and free maintenance updates during the term of the support
period. Please contact our sales department for pricing.
Customers who are not on support may communicate problems, questions or
enhancement requests via FAX or email (see above).
4. System-Specific Release Notes
================================
4.1 IBM AIX
-----------
To read or write a VMS tape, it may be necessary to run
chdev -l <device-name> -a block_size=0
first, where <device-name> is the name of the tape device, for example
`rmt0'. This configures the device to handle variable-length records.
4.2 SGI IRIX
------------
To read or write a tape for use on a non-IRIX system, it is necessary to
use a nonswapping tape device. Nonswapping tape devices typically have
names that end in ns, for example /dev/tapens.
To read or write a VMS tape, it may be necessary to use a tape device
that can handle variable-length records. Tape devices that can handle
variable-length records typically have names ending in v, for example
/dev/mt/tps0d5nsv.
If the appropriate tape device file does not exist, it can be created by
running `MAKEDEV tps' as root.
4.3 Solaris
-----------
To read or write a VMS tape, it may be necessary to reconfigure a kernel
tape driver to handle variable-length records.
The file /kernel/drv/st.conf specifies a comma-separated list of
properties for each supported tape drive class, such as `DAT'. The third
field in a property list must be 0 if the corresponding class of tape
drives is to be used for accessing VMS tapes.
If changes are made to /kernel/drv/st.conf, it is necessary to run
rem_drv st
add_drv st
as root for the changes to take effect.
4.4 SCO
-------
To read or write a tape using Vbackup on SCO OpenServer 5, it is
necessary to run
tape -a 0 setblk <device>
first, where <device> is the tape device, e.g. /dev/rmt/sc0s2.
On SCO 3.x, it is not possible to read or write tapes using Vbackup.
4.5 Other systems
-----------------
To read or write a VMS tape, it is generally necessary to use a tape
device that handles variable-length records.
To test whether a tape device handles variable-length records, load a
scratch tape into the drive and run
dd if=/bin/ls bs=80 of=<device-path>
where <device> is the path to the device, for example /dev/rmt0. If that
command fails, then the device cannot handle variable-length records.
Boston Business Computing technical support may be able to provide
assistance in reconfiguring the device to solve the problem.
5. Known Problems and Limitations
=================================
Vbackup currently does not save HP-UX and AIX access control lists (ACLs)
or HP-UX network-special files, though it warns when not saving them.
1/4-inch cartridge tapes may not be portable between UNIX and VMS
systems.
Vbackup does not translate VAX RMS indexed files to a format recognized
by the UNIX operating system.